-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(table): react table schema order #1829
Conversation
b957630
to
41e6d14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny nitpicks and a typo, otherwise good to go! Thanks for taking this on and the updates are 🔥!
41e6d14
to
5ff56a6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several spelling and grammar suggestions. You did an excellent job explaining the schema/header situation! Thanks!
553403e
to
244e8f8
Compare
This will be used in the argsTable output for Storybook
244e8f8
to
2bccf51
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Description
A Sage support request identified an issue with Data formatting when using Schema.
Use the two images below as a reference. The first image shows the schema and the data used. The second image is the rendered table.
There are a couple of commits in this PR.
Commit 1: Is the first to the problem mentioned above
Commit 2: Updates the React PropTypes. This is to be used in the Storybook
ArgsTable
.Commit 3: Updates the Documentation for Storybook.
Testing in
sage-lib
Here is a loom video...excuse my vocals. I was tripping over my words
Related